Thanks for sending this pull request! Adding the limit option is reasonable, but we'd like to make the new option to be open to future enhancement. So can you create new SessionSettings class (in the same way with ModelSettings) and move the limit parameter as the first and only property in it?

Thanks for the feedback! I've refactored the implementation, following the same pattern as ModelSettings.

Changes made:

• Created SessionSettings dataclass with limit as the first property
• Added session_settings parameter to all session constructors and from_url/ from_address method
• Integrated SessionSettings into RunConfig for runtime overrides
• Added resolve() method for merging settings (base + override)
• Updated all 7 session implementations consistently

I believe this is extensible for future properties. For example, I'd like to add branch_id support for conversation branching in AdvancedSQLiteSession (and a potential AdvancedSQLAlchemySession). If you're open to it, I can also implement it since I need it for my use case anyway.

Let me know if it needs any adjustments